chore: Bump version to 0.9.0, update dep list and changelog#2223
chore: Bump version to 0.9.0, update dep list and changelog#2223blackmwk merged 1 commit intoapache:mainfrom
Conversation
kevinjqliu
left a comment
There was a problem hiding this comment.
LGTM, ty!
i checked against https://rust.iceberg.apache.org/release.html
- looked for
0.8.0in codebase - ran
python3 ./scripts/dependencies.py checklocally (a fewlicense-not-encounteredandlicense-exception-not-encountered, we can deal with it separately)
| * feat!(io): Implement Storage for OpenDal (#2080) by @CTTY in https://github.com/apache/iceberg-rust/pull/2080 | ||
|
|
||
| * **Compatibility:** | ||
| * chore: Update MSRV to 1.91.0 (#2204) by @xanderbailey in https://github.com/apache/iceberg-rust/pull/2204 |
There was a problem hiding this comment.
is there benefits to bumping msrv even further? For example, 1.92.0 was released on: 11 December, 2025 (which is within 3 months from latest rust release)
From README:
Iceberg Rust is built and tested with stable rust, and will keep a rolling MSRV (minimum supported rust version). At least three months from latest rust release is supported. MSRV is updated when we release iceberg-rust.
There was a problem hiding this comment.
This is a good point! bumping MSRV to 1.92 makes sense to me. I'll take a look at this
There was a problem hiding this comment.
Posted another PR to bump MSRV,
#2224
I'll update this PR after that one is merged
blackmwk
left a comment
There was a problem hiding this comment.
Thanks @CTTY for this pr and @kevinjqliu for review!
) ## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes apache#123` indicates that this PR will close issue apache#123. --> - A part of release work: apache#2213 ## What changes are included in this PR? - Version bump to 0.9.0 - Update dep list - Update CHANGELOG.md <!-- Provide a summary of the modifications in this PR. List the main changes such as new features, bug fixes, refactoring, or any other updates. --> ## Are these changes tested? NA <!-- Specify what test covers (unit test, integration test, etc.). If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? -->
Which issue does this PR close?
What changes are included in this PR?
Are these changes tested?
NA